Skip to content

Update dependency sass to v1.97.3#2337

Merged
spaceninja merged 1 commit intomainfrom
renovate/sass-1.x
Feb 4, 2026
Merged

Update dependency sass to v1.97.3#2337
spaceninja merged 1 commit intomainfrom
renovate/sass-1.x

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Feb 4, 2026

This PR contains the following updates:

Package Change Age Confidence
sass 1.93.21.97.3 age confidence

Release Notes

sass/dart-sass (sass)

v1.97.3

Compare Source

  • Fix a bug where nesting an at-rule within multiple style rules in plain CSS
    could cause outer style rules to be omitted.

v1.97.2

Compare Source

  • Additional fixes for implicit configuration when nested imports are involved.

v1.97.1

Compare Source

v1.97.0

Compare Source

  • Add support for the display-p3-linear color space.

v1.96.0

Compare Source

  • Allow numbers with complex units (more than one numerator unit or more than
    zero denominator units) to be emitted to CSS. These are now emitted as
    calc() expressions, which now support complex units in plain CSS.

v1.95.1

Compare Source

  • No user-visible changes.

v1.95.0

Compare Source

  • Add support for the CSS-style if() function. In addition to supporting the
    plain CSS syntax, this also supports a sass() query that takes a Sass
    expression that evaluates to true or false at preprocessing time depending
    on whether the Sass value is truthy. If there are no plain-CSS queries, the
    function will return the first value whose query returns true during
    preprocessing. For example, if(sass(false): 1; sass(true): 2; else: 3)
    returns 2.

  • The old Sass if() syntax is now deprecated. Users are encouraged to migrate
    to the new CSS syntax. if($condition, $if-true, $if-false) can be changed to
    if(sass($condition): $if-true; else: $if-false).

    See the Sass website for details.

  • Plain-CSS if() functions are now considered "special numbers", meaning that
    they can be used in place of arguments to CSS color functions.

  • Plain-CSS if() functions and attr() functions are now considered "special
    variable strings" (like var()), meaning they can now be used in place of
    multiple arguments or syntax fragments in various CSS functions.

v1.94.3

Compare Source

  • Fix the span reported for standalone % expressions followed by whitespace.

v1.94.2

Compare Source

Command-Line Interface
  • Using --fatal-deprecation <version> no longer emits warnings about
    deprecations that are obsolete.
Dart API
  • Deprecation.forVersion now excludes obsolete deprecations from the set it
    returns.
JS API
  • Excludes obsolete deprecations from fatalDeprecations when a Version is
    passed.
Node.js Embedded Host
  • Fix a bug where a variable could be used before it was initialized during
    async compilation.

v1.94.1

Compare Source

  • No user-visible changes.

v1.94.0

Compare Source

  • Potentially breaking compatibility fix: @function rules whose names
    begin with -- are now parsed as unknown at-rules to support the plain CSS
    @function rule. Within this rule, the result property is parsed as raw
    CSS just like custom properties.

  • Potentially breaking compatibility fix: @mixin rules whose names begin
    with -- are now errors. These are not yet parsed as unknown at-rules because
    no browser currently supports CSS mixins.

v1.93.3

Compare Source

  • Fix a performance regression that was introduced in 1.92.0.

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@changeset-bot
Copy link

changeset-bot bot commented Feb 4, 2026

⚠️ No Changeset found

Latest commit: 995f991

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@netlify
Copy link

netlify bot commented Feb 4, 2026

Deploy Preview for cloudfour-patterns ready!

Name Link
🔨 Latest commit 995f991
🔍 Latest deploy log https://app.netlify.com/projects/cloudfour-patterns/deploys/6982965ba165f400089416b0
😎 Deploy Preview https://deploy-preview-2337--cloudfour-patterns.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@renovate renovate bot force-pushed the renovate/sass-1.x branch 5 times, most recently from 0e60077 to 8a636e6 Compare February 4, 2026 00:41
@renovate renovate bot force-pushed the renovate/sass-1.x branch from 8a636e6 to 995f991 Compare February 4, 2026 00:44
@spaceninja spaceninja merged commit a8f9db9 into main Feb 4, 2026
9 checks passed
@spaceninja spaceninja deleted the renovate/sass-1.x branch February 4, 2026 00:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant